Description

Fixes #{issue_number}: A few words or sentences describing the changes proposed in this pull request (PR).

Known TODOs:

• documentation still refers to pip
• explicitly copying all pyproject.toml files in the Dockerfiles is a bit ugly, but can't find a better way
• The base branch needs some work (see PR comment)
• uv sync --all-extras --all-packages is currently needed to get pytest. I'd expect just extras to be needed. Do I need to add extras section to root pyproject and link to workspace extras?
• Do we need a mechanism to ensure that changes to pyproject.toml files are reflected in the uv.lock file so it can be committed too?
• Why do we need to specify setuptools in pixl_dcmd just for the sake of pydicom? Shouldn't it be responsible for its own dependencies?
• Do we need to make use of dependency groups?

Type of change

Please delete options accordingly to the description.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Suggested Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have commented my code, particularly in hard-to-understand areas.
• I have passed on my local host device. (see further details at the CONTRIBUTING document)
• Make sure your branch is up-to-date with main branch. See CONTRIBUTING for a general example to syncronise your branch with the main branch.
• I have requested review to this PR.
• I have addressed and marked as resolved all the review comments in my PR.
• Finally, I have selected squash and merge